Powerline communication device

ABSTRACT

A Powerline Communications (PLC) device includes processing circuitry, memory coupled to the processing circuitry, and a PLC interface coupled to the processing circuitry. The PLC device transmits a plurality of PLC queries, two of the plurality of PLC queries complying with differing PLC communication standards, receives a plurality of responses from a plurality of other PLC devices, responses received from two PLC devices complying with differing PLC communication standards, directs the two PLC devices to transmit communications according to respective differing PLC communication standards in an attempt to avoid PLC communication conflicts. The differing PLC communication standards may include a HomePlug communication standard and an ITU home networking (G.hn) communication standard. The PLC device may convert communications between the differing PLC communication standards.

CROSS-REFERENCE TO PRIORITY APPLICATION

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. §120, as a continuation, to the following U.S. Utility patentapplication which is hereby incorporated herein by reference in itsentirety and made part of the present U.S. Utility patent applicationfor all purposes:

1. U.S. Utility application Ser. No. 13/246,433, entitled “PowerlineCommunication Device,” filed Sep. 27, 2011, pending, which claimspriority pursuant to 35 U.S.C. §119(e) to the following U.S. ProvisionalPatent Application which is hereby incorporated herein by reference inits entirety and made part of the present U.S. Utility patentapplication for all purposes:

-   -   a. U.S. Provisional Application Ser. No. 61/503,060, entitled        “Powerline Carrier Device and System,” filed Jun. 30, 2011, now        expired.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to powerline communications and inparticular, powerline communication devices, and systems of usetherefore.

2. Description of the Related Art

With the growing need for the exchange of digital content (e.g. MP3audio, MPEG4 video and digital photographs) there is a widely recognizedneed to improve digital communication systems. Powerline communication(PLC) is a technology that encodes data in a signal and transmits thesignal on existing electricity powerlines in a band of frequencies thatare not used for supplying electricity. Accordingly, PLC leverages theubiquity of existing electricity networks to provide extensive networkcoverage. Furthermore, since PLC enables data to be accessed fromconventional power-outlets, no new wiring needs to be installed in abuilding (or different parts of a building). Accordingly, PLC offers theadditional advantage of reduced installation costs.

Referring to FIG. 1, a household 100 typically has a distributed mainswiring system (not shown) consisting of one or more ring mains, severalstubs and some distribution back to a junction box 112. In otherconstructs the distributed mains wiring system has a breaker box withcircuits routed there from in a star configuration. For the sake ofexample, the household 100 has four rooms 104, 106, 108, and 120. Eachroom 104, 106, 108, and 120 may have a different number of outlets andother mains connections. For example, room 104 may have only oneconnection 122, room 106 may have two connections 124, 126, room 108 mayhave three connections 128, 130, 132 and room 120 may have sixconnections 134, 136, 138, 140, 142, 144.

Accordingly, there are a variety of distances and paths betweendifferent power outlets in the household 100. In particular, the outletsmost closely located to each other are those on multi-plug strips, andthe outlets furthest away from each other are those on the ends of stubsof different ring mains (e.g. power outlets in the garden shed and theattic). Communication between these furthest outlets typically passesthrough the junction box 112. Nonetheless, the majority of outletsassociated with a particular application (e.g. Home Cinema) are normallylocated relatively close together.

Because the channel capacity of a powerline and connectors attenuatesaccording to, amongst other features, the frequency of a transmittedsignal, current generation PLC systems have been developed to transmitsignals at relatively low frequencies (i.e. below 30 MHz) and therebyobtain suitable transmission distances. However, the use of such lowtransmission frequencies limits the maximum data throughput obtainableby PLC systems. Only recently have powerline systems extended beyond 30MHz, which causes problems due to regulations that require lowerinjected power above 30 MHz. This requirement places additional demandson the dynamic range of transceivers servicing PLC communications inthese higher frequency ranges.

The processes of receiving analog signals and injecting modulatedsignals are treated differently by different PLC communicationstandards. A number of powerline communication standards have beendefined. These include the Homeplug 1.0/1.1 standards, the Homeplug AVstandard, the CEPCA standard, the Digital Home Standard, IEEE 1901, andITU-T G.9960. Current PLC approaches often include some analogconditioning to the signal-path (e.g., low-pass filtering foranti-aliasing or smoothing, or AC coupling to remove the low-frequency[<<1 KHz] high voltage content of the electricity mains). However,because differing PLC communication standards support differingcommunication bands, differing modulations, channel bandwidths, etc.,PLC devices typically service only a single PLC communication standard.In common with most communication systems, one of the main problems withprior art PLC systems is obtaining high throughput and wide coverage atreasonable implementation cost, whilst maintaining compatibility withexisting technologies. There is, therefore, a need for improved PLCsystems that overcome the above and other problems.

Communications within the household 100 or within other premises mayalso be serviced by a Wireless Local Area Network (WLAN), a cellularnetwork, millimeter wave communications, e.g., 60 GHz, Wireless PersonalArea Network (WPAN), Cable Modem Network, Local Area Network (LAN), andother communication techniques. Each of these communication types hasits respective benefits and shortcomings. None of these communicationtypes is typically able to provide a full coverage solution within thehousehold 100 (or other premises). The shortcoming of all wiredtechnologies is the lack of mobility thereof. Shortcomings of allwireless technologies are coverage holes, which are typical,interference from other wireless devices, including competing wirelessdevices, Radar, etc., and bandwidth limitations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a household having a plurality ofpower outlets;

FIG. 2 is a block diagram illustrating a Powerline Communication (PLC)device constructed according to one or more embodiments of the presentinvention;

FIG. 3 is a block diagram illustrating various PLC (and other)communication standards that operate or are modified to operateaccording to one or more embodiments of the present invention;

FIG. 4 is a system diagram illustrating a premises in which at least onePLC device resides that operates according to one or more embodiments ofthe present invention;

FIG. 5 is a system diagram illustrating a premises in which at least onePLC device resides that operates according to one or more embodiments ofthe present invention;

FIG. 6 is a block diagram illustrating a PLC interface that is capableof servicing multiple PLC communication standards and in bridging PLCcommunications between differing PLC communication standards accordingto one or more embodiments of the present invention;

FIG. 7 is a flow chart illustrating operations according to one aspectof the present invention for managing PLC devices on shared media thatsupport differing PLC (and other) communication standards;

FIG. 8 is a flowchart illustrating operations according to one or moreembodiments of the present invention for determining capabilities of PLCcommunication devices coupled thereto and for bridging communicationsbetween differing and incompatible PLC communication standards;

FIG. 9 is a flowchart illustrating operations according to one or moreembodiments of the present invention for servicing communications usingboth PLC communication standard format communications and non-PLCcommunication standard format communications; and

FIG. 10 is a flowchart illustrating operations according to one or moreembodiments of the present invention for concurrently using PLC andnon-PLC communications to service a single communication.

DETAILED DESCRIPTION

FIG. 2 is a block diagram illustrating a Powerline Communications (PLC)device constructed according to one or more other embodiments of thepresent invention. The PLC device 200 supports PLC operations accordingto one or more PLC communication standards. The PLC device 200 may becoupled to a power plug, e.g., into a wall plug 122, 124, 126, 128, 130,132, 134, 136, 138, 140, 142, or 144 of FIG. 1. The PLC device 200performs/supports the various operations and includes the variousstructures further described herein according to one or more embodimentsof the present invention. In some embodiments, the PLC device 200 may bepermanently installed within a home or other premises.

The PLC device 200 includes a PLC interface 206 that includes a powerplug interface 208, an Analog Front End (AFE) 210, and a Digital FrontEnd (DFE) 212. Generally the AFE 210 includes analog signal processingelements while the DFE 212 includes digital signal processing elements.At least one Analog to Digital Converter (ADC) and at least one Digitalto Analog Converter (DAC) service analog to digital and digital toanalog signal conversion operations, respectively. Various components ofthe PLC interface 206 as they relate to embodiments of the presentinvention will be described further herein.

The PLC device 200 also includes one or more other communicationinterfaces, including a Wireless Wide Area Network (WWAN) interface 214,e.g., a WiMAX interface, a Wireless Local Area Network (WLAN) interface216, e.g., an 802.11x interface, a Wireless Personal Area Network (WPAN)interface 218, e.g., a Bluetooth interface, a 60 GHz interface 220(millimeter wave interface), a Local Area Network (LAN) interface 222,e.g., an Ethernet interface, a cable interface, e.g. Multimedia overCoax Alliance (MoCA) interface 224, an optical interface 226, a NearField Communication (NFC) OF 228, an Infra-Red OF 230, and/or an RF TagOF 232. The user should appreciate that the PLC device 200 may bridgecommunications between a power plug and one or more devices, e.g.,between the power plug and a desktop computer, a laptop computer, atouchpad computer, an appliance, a television, another entertainmentsystem device, etc., via the PLC interface 206 and one or more of theother communication interfaces 214, 216, 218, 220, 222, 224, 226, 228,230, and/or 232.

The processing module 202 may include one or more of a system processor,a digital signal processor, a processing module, dedicated hardware, anapplication specific integrated circuit (ASIC), or other circuitry thatis capable of executing software instructions and for processing data.In particular, the processing module 202 is operable to support MediumAccess Control (MAC) management, communications bridging management, andother management of the communications circuitry of the PLC device 200.The memory 204 may be RAM, ROM, FLASH RAM, FLASH ROM, optical memory,magnetic memory, or other types of memory that is capable of storingdata and/or instructions and allowing processing circuitry to accesssame. The processing module 202 and the memory 204 supports operationsof embodiments of the present invention as further described herein.

FIG. 3 is a block diagram illustrating various PLC (and other)communication standards that operate or are modified to operateaccording to one or more embodiments of the present invention. Currentlyexisting PLC communication standards include the HomePlug family ofoperations, including the 1.0, AV1.1, AV2, and GP operations, and theHD-PLC operations. Generally, the HomePlug family of PLC communicationstandards is incompatible with the HD-PLC communication standard. TheHomePlug PLC communication standard is widely deployed while HD-PLC isprimarily deployed in Japan.

The IEEE 1901 specification includes a newer PLC communication standardthat has two different PHY layers, one based on OFDM modulation(interoperable with HomePlug AV1.1), and another based on Waveletmodulation (interoperable with HD-PLC). Each PHY layer is optional, andimplementers of the communication standard may, but are not required toinclude both. Devices that use the OFDM PHY only would not interoperatewith devices based on the Wavelet PHY. The OFDM PHY is derived fromHomePlug AV.

The IEEE 1905.1 specification defines an abstraction layer for multiplehome networking technologies. IEEE 1905.1 provides a common data andcontrol Service Access Point to the heterogeneous home networkingtechnologies described in the following specifications: IEEE 1901, IEEE802.11x, IEEE 802.3x and Multimedia over Coax Alliance (MoCA) 1.1. TheIEEE 1905.1 standard is extendable to work with other home networkingtechnologies. The abstraction layer supports dynamic interface selectionfor transmission of packets arriving from any interface (upper protocollayers or underlying network technologies). End-to-end Quality ofService (QoS) is supported. Also specified are procedures, protocols andguidelines to provide a simplified user experience to add devices to thenetwork, to set up encryption keys, to extend the network coverage, andto provide network management features to address issues related toneighbor discovery, topology discovery, path selection, QoS negotiation,and network control and management.

The IEEE 1905.1 layer resides between the media access control andInternet Protocol layers. The 1905.1 abstraction layer intends to makeit easier to install and manage hybrid home networks and will alsoprovide mechanisms for bridging data among different interfaces, i.e.,plug and play.

ITU's G.hn specification is a competing counterpart to IEEE 1901 thatprimarily defines different ways to implement PHY and MAC layers of aPLC device. G.hn is a technology standard that enables serviceproviders, consumer electronics companies, PC makers, and consumers toconnect all types of devices via any wire in the home—coax cable, phonelines and powerlines.

There are a multitude of narrow and broadband PLC technologies beyondIEEE 1901 that already exist. For example, conventional tier twocoexistence mechanisms are included in ISO/IEC 14908, G3 & G3 Lite, HPC&C, ISO/IEC 14543 which employ some form of CSMA/CA. Other PLCcommunication standard technologies do not support any type ofcoexistence other than tier one. Such standards include most currentbroadband PLC offerings, UPB, A10, INSTEON/X-10, Ariane Controls, CEBus,CEA 600.31, TDA 5051A, etc.

With all of these PLC communication standards potentially sharing thesame powerline media and defining use of the same frequency bands, majorproblems arise depending on the particular installation. For example, ifa consumer buys and installs current PLC components, they may notfunction, function inadequately, or may cause major problems withcurrently existing PLC components operating pursuant to other standards.A first tier of conventional coexistence involved PLC frequency spectrumallocation, which has failed because there is no controlling entityenforcing conformance (such as found with over the air transmissions andthe FCC).

The industry is aware of first tier conventional coexistence failures,and is currently attempting to define a second tier conventionalcoexistence scheme to apply to all PLC communication standards.Basically, a second tier approach involves first identifying allstandards that may exist within a current installation, and then equallysplitting available resources (frequency band, available time, etc.)amongst them.

A problem with prior tier one and two coexistence schemes is that afirst group of devices of a first standard might be rather inactive andcould afford to lose available resources, while a second group of secondstandard devices might be very active and could benefit from moreresources. The second group might also involve many more devices thanthat of the first group, or be involved in communication exchanges withmuch higher priority. Communication management operations supported by aPLC device of the present invention address these and additionalproblems.

FIG. 4 is a block diagram illustrating a premises in which at least onePLC device resides that operates according to one or more embodiments ofthe present invention. The premises 400 may be a home, office building,apartment complex, hotel, industrial building, or another type ofstructure. In the particular example of FIG. 4, a WLAN access point 424provides Internet access within the premises 400 and is also a PLCdevice constructed according to one or more embodiments of the presentinvention. Also shown within the premises 400 are a plurality of PLCdevices 402, 404, 406, 408, 410, 412, and 414. One or more of these PLCdevices 402, 404, 406, 408, 410, 412, and 414 may be provided by thepremises 400 owner/operator while other of these PLC devices may bebrought into the premises 400 by a customer. In particular, PLC device402 services electronic device 428, PLC device 404 services device 430,PLC device 408 services electronic device 432, and PLC device 414services electronic device 434. Each of these devices 428, 430, 432, and434 may be owned by the premises 400 owner or may be owned by a premises400 visitor.

According to one or more embodiments of the present invention, one ormore of these PLC devices 402, 404, 406, 408, 410, 412, 414, and 424supports one or more differing PLC communication standards. For examplePLC device 402 supports PLC communication standard 1, PLC device 404supports PLC communication standard 1, PLC device 406 supports PLCcommunication standards 1 and 2, PLC device 408 supports PLCcommunication standard 3, PLC device 410 supports PLC communicationstandard 3, PLC device 412 supports PLC communication standard 3, andPLC device 414 supports PLC communication standards 2 and 3, and PLCdevice 424 supports PLC communication standards 1 and 3. As will befurther described herein the differing PLC communication standards maybe wideband, narrowband, consistent with one another, and/orinconsistent with one another. These PLC communication standards may beone of the PLC communication standards described with reference to FIG.3 or may be another PLC communication standard.

According to one or more embodiments of the present invention, one ormore of the PLC devices 402, 404, 406, 408, 410, 412, 414, and 424 mayserve as masters of the powerline media servicing the premises 400, maybridge communications across differing PLC communication standards,and/or may bridge communications between PLC communications and non-PLCcommunications. Several of these operations will be described hereinsubsequently. In some embodiments, each PLC standard will have a uniquemaster, with differing PLC devices serving as masters for differing PLCcommunication standards. Likewise, each supported non-PLC communicationstandard may have its own master.

FIG. 5 is a block diagram illustrating a premises in which at least onePLC device resides that operates according to one or more embodiments ofthe present invention. The premises 500 may be a home, office building,apartment complex, hotel, industrial building, or another type ofstructure. The premises 500 includes a plurality of spaces 502, 504,506, and 508, each of which may be a room, an apartment, an office, anindustrial space, or another type of unit. Installed within the premises500 are a plurality of PLC devices 510, 512, 514, 516, 518, 520, and522. Also installed in the premises is a PLC device serving as a Gateway524 for communications services. Each of the PLC devices 510-522illustrated has a structure same or similar to the structure describedwith reference to FIGS. 2-4 and 6 and that operates according to theoperations described with reference to FIGS. 7-10.

Also located in the premises 500 are a number of appliances 550, 552,554, 556, 558, 560, 562, 564, 566, and 568. These appliances may bekitchen appliances such as refrigerators, freezers, stoves, ovens,dishwashers, trash compactors, small appliances, ice makers, etc.Further, these appliances may be office appliances such as computers,printers, scanners, monitors, etc. Further still these appliances couldbe industrial equipment, air conditioning units, heating units,ventilation units, fans, etc. The scope of the term appliance is notlimited by the examples provided herein.

According to one aspect of the present invention, any of the PLC devicesin the premises is capable of providing network service to theappliances along with node tagging support. One or more of theappliances may have a conventional tag, e.g., an RFID, NFC tag, onedimensional or two dimensional code, or another type of tag. One or moreof the illustrated PLC devices has the ability to identify proximatelylocated appliances (devices) using near field communication and/or RFIDsand/or bar codes. In such case, the device may query locally allpotential RF tag enabled devices for response in identifying basedthereupon. Further, near field communication may be employed by thedevice to identify proximately located devices. With each device labeledor identified, this information may be uploaded to a central location toat least logically map the location of these devices with the PLC devicethat does the querying.

This type of technique could be used to support “network in a box”functionality within a home or business. This network in a box mayinclude RF tags for network enabled devices in the home (or simply loaddevices). This invention may also be extended with the use of wirelessbeam forming to further identify a fixed physical location of thedevices with respect to other devices. By using wireless beam forming,the logical locations of each of the devices may be related to oneanother and the physical positioning of the beam forming technique.

According to a multi-communication technique installation within a home,one type of communication service may be wireless communications thatare serviced by devices that bridge from a powerline communicationscommunication link to a wireless link. For example, this type of devicemay provide 60 GHz wireless communications within a particular room.Further, another type of device may provide 802.11 communications with aparticular part of the structure. Further, another bridging type devicemay bridge between PLC and Ethernet communications.

In such case, a software application is downloaded onto a phone 570 foruse in mapping wireless services available within a home. The phone ortablet device 570 would have at least one wireless interface servicingWLAN or 60 GHz that would be able to determine service levels in allportions of the home/structure. In such case, the phone/tablet may alsohave a GPS receiver or another type of mapping location awareness thatis employed for characterizing available communication services withinthe home. RFID/NFC tags associated with either or both the phone/tabletand a particular access point (powerline or otherwise) could interactalong with position information to assist in generating such map. A userwould enable the application and do a walkabout within the home tocharacterize communications characteristics that are available withinvarious portions within the home. The data collected by the phone/tabletmay be subsequently used to determine where additional points ofcommunications are required, e.g. additional PLC/802.11 or PLC/60 GHzdevices are required.

According to one aspect of the present invention, which will bedescribed further with reference to FIGS. 6-10, a PLC device supportsoperations across multiple PLC communication standards. Each suchmulti-standard PLC node can be configured to perform virtual bridging insupport of these operations. For example, an upstream DSL AP 524provides IP connectivity (Internet access, wideband Media, Phone, etc.)and is configured internally to support a downstream PLC pathway thatsupports two competing PLC communication standard technologies. A userplugs in a first PLC bridging device 510 (operating further downstreampursuant to the first industry standard) to service a PC (not shown) viaa CAT5 cable and PLC to Ethernet bridging. Next, a user plugs in asecond PLC bridging device 512 (bridging PLC to WiFi) that supports boththe first and second industry standards. At that point, the AP 524switches from operating fully pursuant to the first industry standard toa slotted operation, toggling between the first standard and the second.Instead of the second PLC device 512 merely acting like the first PLCdevice 510 in selecting only one standard and slot in which to conform,it toggles back and forth between the first and second industrystandards to take advantage of all available time domain bandwidth. Todo so, however requires that communication addressing is maintainedseamless throughout. This may be handled by supporting exchanges via oneslot, while supporting exchanges via “virtual bridging” in the other(e.g., encapsulation and forwarding—or address substitution andforwarding).

FIG. 6 is a block diagram illustrating a PLC interface that is capableof servicing multiple PLC communication standards and in bridging PLCcommunications between differing PLC communication standards accordingto one or more embodiments of the present invention. The PLC interface206 may be same/similar to the PLC interface 206 of FIG. 2, and is ableto service a plurality of differing PLC communication standards. The PLCinterface 206 includes PLC interface processing circuitry 602, anarrowband PLC interface 604, a first wideband PLC interface 606, asecond wideband PLC interface 608, and a PLC media interface 610. ThePLC media interface 610 couples PLC communications standardcommunication signals onto the PLC media and from the PLC media. Thenarrow band PLC interface 604 services narrowband PLC communicationstandard communications, e.g. according to one of the standardspreviously described. Both the first wideband PLC interface 606 and thesecond wideband PLC interface 608 service communications for at leastone wideband PLC communication standard, such as one or more of the HPAVand G.hn standards previously described and according to one or moreembodiments of the present invention.

PLC interface processing circuitry 602 supports operations previouslydescribed herein with reference to FIGS. 2-5, and that will further bedescribed with reference herein to FIGS. 7-10. The PLC interfaceprocessing circuitry 602 executes operations for PLC MAC management, PLCcore existence management, and communication bridging/forwarding. Thisfunctionality may be instantiated in hardware, software, or acombination of hardware and software. The PLC interface processingcircuitry 602 may be a microprocessor, digital signal processor,specialized hardware, or a combination of these and/or other circuitrythat is capable of performing the functionality described herein withreference thereto.

FIG. 7 is a flow chart illustrating operations according to one aspectof the present invention. The operations 700 of FIG. 7 begin with thePLC device 200 sending out queries to PLC devices according to a firstPLC operating specification (Step 702). The PLC device 200 then waitsfor devices of the particular PLC operating specification to respond andinterrogates each responding device for its communicationbandwidth/throughput and Quality of Service (QoS) requirements (Step704). The PLC device 200 then determines whether it has completedquerying all PLC device types (Step 706). Device types may include bothnarrowband and wideband device types, which have been previouslydescribed herein above. When further device type querying is required,operation returns to Step 702. When all querying is complete, operationproceeds to Step 708, where the PLC device 200 may determine Frequencydomain and/or Time domain allocations for each responding device.

The PLC device 200 then directs each responding device with itscorresponding Frequency domain and Time domain allocation (Step 710).The PLC device 200 then operates with this allocation until a timeout orother triggering event occurs (Step 706). When such a timeout ortriggering event occurs, operation returns to Step 702, where thequerying operations commence again.

In particular, the PLC device transmits a plurality of PLC queries, eachPLC query respective to a particular PLC communication standard, two ofthe plurality of PLC queries complying with differing and incompatiblePLC communication standards. The PLC queries are sent with theexpectation that PLC devices sharing the PLC media and the PLCcommunication standard capability will respond, indicating that they arepresent on the PLC media. The responses may also indicate capabilitiesand communication requirements of the responding devices. Each supportedPLC communication standard may define such a query or a similarmessage/beacon. For example, G.hn has a MAP message that may serve asthe PLC query in some embodiments, with or without modification. OtherPLC communication standards have similar messages, which serve similarpurposes.

In response to the PLC queries, the PLC device receives a plurality ofresponses from a plurality of other PLC devices, two responses receivedfrom respective PLC devices complying with two differing andincompatible PLC communication standards. The PLC device then directseach of the two PLC devices to transmit communications of the differingand incompatible PLC communication standards in an attempt to avoid PLCcommunication conflicts. Alternately, the PLC device may establishnon-PLC communications with a remote communications device and bridgecommunications between the remote PLC device and a remote non-PLCdevice.

The operations 700 may enable a PLC device to allocate first time slotsfor a first one of differing and incompatible PLC communicationstandards and to allocate second time slots for a second one of thediffering and incompatible PLC communication standards. In such case,the first time slots would differ from the second time slots. Thus, withreference again to FIG. 3, the PLC device constructed according to thepresent invention may service both Homeplug and ITU G.hn communicationson the same media by subdividing the times of the media used for each ofthe PLC communication standards to the differing and incompatible PLCcommunication standards. In such case, selecting the first time slotsand the second time slots for allocation to the differing standards, aPLC device constructed and operating according to the present inventionmay consider the link quality available for each of the PLCcommunication standards, may consider the throughput availability of thePLC devices that support the differing incompatible PLC communicationstandards. Further, the PLC device in performing the operations 700 ofFIG. 7 may consider the data security requirements of the one or morePLC devices sharing the PLC media and/or the data type for transmissionbetween one or more of the PLC devices.

Referring again to FIG. 4, the operations 700 of FIG. 7 may be employedby the infrastructure 400 of FIG. 4 wherein one of the PLC devicesmanages the incompatible communications upon the PLC medium of thepremises 400. In such case, for example, one of the PLC devices, e.g.406, would manage communication flow between devices supportingstandards 1 and 2. Likewise, another one of the PLC devices 424 wouldmanage communications between the devices supporting PLC communicationstandards 1 and 3. Further, with the example of FIG. 4, the PLC device414 that supports PLC communication standards 2 and 3 would managecommunications within the premises 400 according to the standards 2 and3. In such case, PLC devices 406, 414, and 424 would intercommunicatewith one another in an effort to avoid conflict amongst the PLC devicesoperating according to the differing communication standards 1, 2, 3. Insuch case, the available communication bandwidth may be subdivided intothree different recurring time slots to support communications with thethree differing PLC communication standards. This technique of theoperation 700 of FIG. 7 may be extended within the premises of FIG. 4 orother premises to support a further additional PLC communicationstandard.

Referring again to FIG. 7, the operations at step 708 may includeallocating the first frequency band for a first one of differing andincompatible PLC communication standards and allocating a secondfrequency band for a second one of the differing and incompatible PLCcommunication standards. Similarly to the time division segregation thatwas previously described, a frequency band available for communicationsby PLC devices may be subdivided for use by differing PLC communicationstandards devices. In such cases, the determination of what frequencybands to allocate may be based on the link quality available between PLCdevices, the throughput availability between PLC devices, data securityrequirements of the PLC devices, QoS requirements of the PLC devices,and/or the data type for transmission of the PLC devices. In such case,if PLC devices supporting a consistent same standard require high datathroughput, more of an available frequency spectrum may be assigned toone of the PLC communication standards as compared to a differing one ofthe PLC communication standards. Further, time division multiplexing andfrequency division multiplexing may also be employed to subdivideavailable communication capacity on PLC media for a plurality of PLCdevices. Likewise, the concepts of the present invention may be extendedto allow for PLC devices to support differing PLC communicationsstandards that both use OFDM front ends but with differing communicationmethodologies to subdivide the tones available on the OFDM carriers fordiffering PLC communication standards.

With the operations 700 of FIG. 7, the PLC device 202 supports anintelligent, adaptive coexistence management PLC architecture whereinmultiple PLC communication standards are allocated portions of theavailable bandwidth based on current demand and traffic QoS.

The operations 700 of FIG. 7 may be expanded to operate across multiplemediums accessible by the PLC device 200 of FIG. 2, acting as a networkmanager. In such case, the PLC device provides an adaptive managementelement within or via an (e.g., 1905.1) abstraction layer that optimizesoverall communication flow across all underlying mediums (air,powerline, coax, telephone line, Ethernet, cellular, etc.). For example,PLC devices participating in a home environment (such as a client's pc,smart-phones, etc.) often have two or more communication means definedby differing Industry Standards such as IEEE 1901, Femtocell, MoCA,WiFi, etc. For a given situation in a specific installation, there is anoptimal traffic configuration that such adaptive management elementdetects and directs. It does this by first gathering information aboutunderlying node capabilities, network conditions and limitations, andunderlying data-flow. Based thereon, re-allocation commands aredelivered forcing migration to new configurations on the fly.

When multiple PLC devices (multiples of PLC devices 200) exist within aparticular installation, operations may require Cross-MediumCoexistence. For example, where a first PLC device supports first andsecond PLC communication standards and a second PLC device supportsthird and fourth PLC communication standards and where the first andthird PLC communication standards operate on the same medium incompetition (via single medium coexistence sharing) or in directconflict, an abstraction layer (e.g., similar or within IEEE 1905.1)defines that either the first or the second PLC device relinquishes allor at least some use of the corresponding first or third standard,correspondingly, and is forced to rely at least more heavily if notentirely on the second or fourth standards instead. The abstractionlayer makes its decision based on (i) channel conditions underlying thefirst, second, third and fourth standards; (ii) node impact (cost,power, etc.); (iii) user setup or real time preferences; (iv) underlyingQoS concerns, etc.

Further, a PLC device 200 of the present invention may supportmulti-medium Mesh operations that perform flooding and/or routing ofcommunications across multiple mediums concurrently. In such case, therouting of data by the PLC device 200 may be performed such that data isrouted across multiple data paths, e.g., two or more of PLC path, WLANpath, LAN path, MoCA path, etc. The PLC device 200 may serve as anintermediate routing node that makes media routing decisions based uponmedia loading, data type, QoS requirements, and other characteristics ofnot only the serviced transaction but the available media paths and thecharacteristics of each media path.

The PLC devices 200 of the present invention may also supportCross-Medium Sub-Streaming, with which a source or middling PLC devicebreaking data flow (stream) into sub-portions (diverging), sending suchsub-portions independently across multiple mediums and finallyreconstructing by a destination or further middling PLC device back intothe original stream (converging). This diverging-converging process canbe nested and occur many times in an overall pathway between a sourceand destination.

One or more PLC devices 200 of the present invention may support VirtualBridging Across Multiple Powerline Modems. Coexistence betweenincompatible PLC communication standards such as HPAV and G.hn may behandled by a time domain sharing, where incompatibilities exist. SomePLC devices may support only one of such multiple standards, whileothers support all. One sharing approach involves a time slot allocationin an equal splitting manner, to yield periods in which a first standarddevice grouping operates and periods wherein a second standard devicegrouping operates. This sharing approach is that each device willoperate only pursuant to one standard throughout.

According to another aspect of the present invention, one or moresupported PLC communication standards may be “disabled’ within the PLCnetwork to avoid conflict and all nodes directed to communicate usingother techniques. In such case, a PLC node may be directed to use WLANcommunications instead of PLC communications when the use of the PLCcommunications would burden the PLC media unduly considering the benefitof allowing instantiation of the PLC communication standard. Thedecision to “disable” the PLC communication standard from use may bebased upon the efficiency pre and post disablement, deliverable QoS preand post disablement, throughput on a node by node basis pre and postdisablement and upon other factors.

FIG. 8 is a flowchart illustrating operations according to one or moreembodiments of the present invention for determining capabilities of PLCcommunication devices coupled thereto and for bridging communicationsbetween differing and incompatible PLC communication standards.Operations 800 commence with a PLC device receiving PLC communicationsfrom a first remote PLC device in a first PLC communication standardformat (Step 802). The PLC device then converts the PLC communicationsfrom the first PLC communication standard format to a second PLCcommunication standard format (Step 804). Then, the PLC device transmitsthe converted PLC communications to a second remote PLC device in thesecond PLC communication standard format (Step 806).

Referring again to FIG. 4, PLC device 406 may bridge communicationsbetween PLC device 402 and PLC device 410. In such case, because the PLCdevice 402 only supports PLC communication standard 1 and PLC device 410only supports PLC communication standard 2. PLC device 406, supportingboth standards 1 and 2, bridges PLC communications between the PLCdevices 402 and 410 according to the operations 700 of FIG. 7. Suchbridging may occur unidirectionally or bidirectionally, based upon theparticular operation employed.

FIG. 9 is a flowchart illustrating operations according to one or moreembodiments of the present invention for servicing communications usingboth PLC communication standard format communications and non-PLCcommunication standard format communications. Operations 900 commencewith a PLC device establishing PLC communications with another PLCdevice via a PLC communication standard format (Step 902). Then, the PLCdevice establishes non-PLC communications with a remote communicationdevice via a non-PLC communication standard (Step 904). The non-PLCcommunication standards may be one or more of LAN communications, WWANcommunications, WLAN communications, coaxial communications, millimeterwave communications, cellular telephony communications, near fieldcommunications, infrared communications, and/or optical communications.In such case, the usage of non-PLC with reference to FIG. 9 indicatesonly that the non-PLC communications do not operate according to a PLCcommunications standard.

Operation 900 continues with the PLC device receiving a communicationfrom the other PLC device in a PLC communication standard format (Step906). The PLC device then converts the communication from the PLCcommunication standard format to a non-PLC communication standard format(Step 908). Then, the PLC device transmits the communication in thenon-PLC communication standard format to the remote communicationsdevice (Step 910). In such case, the communications transmittedaccording to one of the communication types previously described.

The operations 900 of FIG. 9 may be employed with one or more of thedevices of the premises 400 of FIG. 4. In such case, PLC device 424receives a PLC communication in a PLC communication standard format 1and converts the PLC communication to a WLAN communication to therebytransmit the communication to a remote device that supports WLANcommunications, e.g. 428. Likewise, one of the PLC devices of FIG. 4 mayreceive a communication in a WLAN or another communication format,convert that communication to a PLC communication format, and transmitthe communication via the PLC media to another PLC device.

According to another aspect of the PLC/non-PLC bridging operation of thepresent invention, upstream communications may be transmitted in oneformat and downstream communications may be transmitted in anotherformat. For example, if the PLC communications may be transmitted at ahigher data throughput rate, downstream communications may betransmitted via the PLC media. Further, the upstream communications mayhave a lesser throughput rate and may be transmitted via a non-PLCcommunication standard format, e.g. WLAN communications. Theseprinciples may be expanded further with differing communication types tosubdivide between PLC communications and non-PLC communications.

FIG. 10 is a flowchart illustrating operations according to one or moreembodiments of the present invention for concurrently using PLC andnon-PLC communications to service a single communication. Operations1000 commence with splitting a communication into a PLC communicationstandard format portion and a non-PLC communication standard formatportion (Step 1002). The non-PLC communication standard format may beone of those types previously described herein. Then, operation 1000continues with transmitting the PLC communication standard formatportion to a remote communications device via PLC media (Step 1004).Operations 1000 continue with transmitting the non-PLC communicationstandard format portion to the remote communications device via non-PLCmedia (Step 1006). The operations of steps 1004 and 1006 may beperformed simultaneously such that communications transmitted on the PLCmedia and the non-PLC media occur simultaneously or sequentially, eitherstep 1004 or step 1006 occurring first.

The terms “circuit” and “circuitry” as used herein may refer to anindependent circuit or to a portion of a multifunctional circuit thatperforms multiple underlying functions. For example, depending on theembodiment, processing circuitry may be implemented as a single chipprocessor or as a plurality of processing chips. Likewise, a firstcircuit and a second circuit may be combined in one embodiment into asingle circuit or, in another embodiment, operate independently perhapsin separate chips. The term “chip,” as used herein, refers to anintegrated circuit. Circuits and circuitry may comprise general orspecific purpose hardware, or may comprise such hardware and associatedsoftware such as firmware or object code.

The present invention has also been described above with the aid ofmethod steps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claimed invention.

The present invention has been described above with the aid offunctional building blocks illustrating the performance of certainsignificant functions. The boundaries of these functional buildingblocks have been arbitrarily defined for convenience of description.Alternate boundaries could be defined as long as the certain significantfunctions are appropriately performed. Similarly, flow diagram blocksmay also have been arbitrarily defined herein to illustrate certainsignificant functionality. To the extent used, the flow diagram blockboundaries and sequence could have been defined otherwise and stillperform the certain significant functionality. Such alternatedefinitions of both functional building blocks and flow diagram blocksand sequences are thus within the scope and spirit of the claimedinvention. One of average skill in the art will also recognize that thefunctional building blocks, and other illustrative blocks, modules andcomponents herein, can be implemented as illustrated or by discretecomponents, application specific integrated circuits, processorsexecuting appropriate software and the like or any combination thereof.

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. Such an industry-accepted toleranceranges from less than one percent to fifty percent and corresponds to,but is not limited to, component values, integrated circuit processvariations, temperature variations, rise and fall times, and/or thermalnoise. Such relativity between items ranges from a difference of a fewpercent to magnitude differences. As may also be used herein, theterm(s) “coupled to” and/or “coupling” and/or includes direct couplingbetween items and/or indirect coupling between items via an interveningitem (e.g., an item includes, but is not limited to, a component, anelement, a circuit, and/or a module) where, for indirect coupling, theintervening item does not modify the information of a signal but mayadjust its current level, voltage level, and/or power level. As mayfurther be used herein, inferred coupling (i.e., where one element iscoupled to another element by inference) includes direct and indirectcoupling between two items in the same manner as “coupled to.” As mayeven further be used herein, the term “operable to” indicates that anitem includes one or more of power connections, input(s), output(s),etc., to perform one or more its corresponding functions and may furtherinclude inferred coupling to one or more other items. As may stillfurther be used herein, the term “associated with,” includes directand/or indirect coupling of separate items and/or one item beingembedded within another item. As may be used herein, the term “comparesfavorably,” indicates that a comparison between two or more items,signals, etc., provides a desired relationship. For example, when thedesired relationship is that signal 1 has a greater magnitude thansignal 2, a favorable comparison may be achieved when the magnitude ofsignal 1 is greater than that of signal 2 or when the magnitude ofsignal 2 is less than that of signal 1.

The present invention has also been described above with the aid ofmethod steps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the invention.

Moreover, although described in detail for purposes of clarity andunderstanding by way of the aforementioned embodiments, the presentinvention is not limited to such embodiments. It will be obvious to oneof average skill in the art that various changes and modifications maybe practiced within the spirit and scope of the invention.

The invention claimed is:
 1. A Powerline Communications (PLC) devicecomprising: processing circuitry; memory coupled to the processingcircuitry; a PLC interface coupled to the processing circuitry, whereinthe processing circuitry, the PLC interface, and the memory areconfigured to: transmit a plurality of PLC queries, two of the pluralityof PLC queries complying with differing PLC communication standards;receive a plurality of responses from a plurality of other PLC devices,responses received from two PLC devices complying with differing PLCcommunication standards; and direct the two PLC devices to transmitcommunications according to respective differing PLC communicationstandards in an attempt to avoid PLC communication conflicts.
 2. The PLCdevice of claim 1, wherein the processing circuitry, the PLC interface,and the memory are further configured to: receive PLC communicationsfrom a first PLC device in a first PLC communication standard format;convert the PLC communications from the first PLC communication standardformat to a second PLC communication standard format to produceconverted PLC communications; and transmit the converted PLCcommunications to a second PLC device.
 3. The PLC device of claim 1,wherein: a first one of the differing PLC communication standardscomprises a HomePlug communication standard; and a second one of thediffering PLC communication standards comprises an ITU home networking(G.hn) communication standard.
 4. The PLC device of claim 1, wherein indirecting the two PLC devices to transmit communications according torespective differing PLC communication standards in an attempt to avoidPLC communication conflicts, the processing circuitry, the PLCinterface, and the memory are configured to: allocate first time slotsfor a first one of the differing PLC communication standards; andallocate second time slots for a second one of the differing PLCcommunication standards, wherein the first time slots differ from thesecond time slots.
 5. The PLC device of claim 4, wherein the first timeslots and second time slots are selected based upon at least one of:link quality with one or more of the other PLC devices; throughputavailability with one or more of the other PLC devices; data securityrequirements of the one or more of the other PLC devices; Quality ofService requirements of the one or more of the other PLC devices; anddata type for transmission to one or more of the other PLC devices. 6.The PLC device of claim 1, wherein in directing the two PLC devices totransmit communications according to respective differing PLCcommunication standards in an attempt to avoid PLC communicationconflicts, the processing circuitry, the PLC interface, and the memoryare configured to: allocate a first frequency band for a first one ofthe differing PLC communication standards; and allocate a secondfrequency band for a second one of the differing PLC communicationstandards, wherein the first frequency band differs from the secondfrequency band.
 7. The PLC device of claim 6, wherein the firstfrequency band and the second frequency band are selected based upon atleast one of: link quality with one or more of the other PLC devices;throughput availability with one or more of the other PLC devices; datasecurity requirements of the one or more of the other PLC devices;Quality of Service requirements of the one or more of the other PLCdevices; and data type for transmission to one or more of the other PLCdevices.
 8. The PLC device of claim 1, wherein the processing circuitry,the PLC interface, and the memory are further configured to dividecommunications with a remote PLC device between a first PLCcommunication standard and a second PLC communication standard.
 9. ThePLC device of claim 1, wherein the differing PLC communication standardsare selected from the group consisting of the Homeplug 1.0/1.1standards, the Homeplug AV standards, the CEPCA standards, the DigitalHome Standards, the IEEE 1901 standards, and the ITU-T G.9960 standards.10. A method for operating a Powerline Communications (PLC) devicecomprising: transmitting a plurality of PLC queries, two of theplurality of PLC queries complying with differing PLC communicationstandards; receiving a plurality of responses from a plurality of otherPLC devices, responses received from two PLC devices complying withdiffering PLC communication standards; and directing the two PLC devicesto transmit communications according to respective differing PLCcommunication standards in an attempt to avoid PLC communicationconflicts.
 11. The method of claim 10, further comprising: receiving PLCcommunications from a first PLC device in a first PLC communicationstandard format; converting the PLC communications from the first PLCcommunication standard format to a second PLC communication standardformat to produce converted PLC communications; and transmitting theconverted PLC communications to a second PLC device.
 12. The method ofclaim 10, wherein: a first one of the differing PLC communicationstandards comprises a HomePlug communication standard; and a second oneof the differing PLC communication standards comprises an ITU homenetworking (G.hn) communication standard.
 13. The method of claim 10,wherein directing the two PLC devices to transmit communicationsaccording to respective differing PLC communication standards in anattempt to avoid PLC communication conflicts comprises: allocating firsttime slots for a first one of the differing PLC communication standards;and allocating second time slots for a second one of the differing PLCcommunication standards, wherein the first time slots differ from thesecond time slots.
 14. The method of claim 13, wherein the first timeslots and second time slots are selected based upon at least one of:link quality with one or more of the other PLC devices; throughputavailability with one or more of the other PLC devices; data securityrequirements of the one or more of the other PLC devices; Quality ofService requirements of the one or more of the other PLC devices; anddata type for transmission to one or more of the other PLC devices. 15.The method of claim 10, wherein directing the two PLC devices totransmit communications according to respective differing PLCcommunication standards in an attempt to avoid PLC communicationconflicts comprises: allocating a first frequency band for a first oneof the differing PLC communication standards; and allocating a secondfrequency band for a second one of the differing PLC communicationstandards, wherein the first frequency band differs from the secondfrequency band.
 16. The method of claim 15, wherein the first frequencyband and the second frequency band are selected based upon at least oneof: link quality with one or more of the other PLC devices; throughputavailability with one or more of the other PLC devices; data securityrequirements of the one or more of the other PLC devices; Quality ofService requirements of the one or more of the other PLC devices; anddata type for transmission to one or more of the other PLC devices. 17.The method of claim 10, further comprising dividing communications witha remote PLC device between a first PLC communication standard and asecond PLC communication standard.
 18. A Powerline Communications (PLC)device comprising: processing circuitry; memory coupled to theprocessing circuitry; a wireless interface coupled to the processingcircuitry; and a PLC interface coupled to the processing circuitry,wherein the processing circuitry, the PLC interface, and the memory areconfigured to: transmit a plurality of PLC queries, two of the pluralityof PLC queries complying with differing PLC communication standards;receive a plurality of responses from a plurality of other PLC devices,responses received from two PLC devices complying with differing PLCcommunication standards; and direct the two PLC devices to transmitcommunications according to respective differing PLC communicationstandards in an attempt to avoid PLC communication conflicts.
 19. ThePLC device of claim 18, wherein the processing circuitry, the PLCinterface, and the memory are further configured to: receive PLCcommunications from a first PLC device in a first PLC communicationstandard format; convert the PLC communications from the first PLCcommunication standard format to a second PLC communication standardformat to produce converted PLC communications; and transmit theconverted PLC communications to a second PLC device.
 20. The PLC deviceof claim 18, wherein: a first one of the differing PLC communicationstandards comprises a HomePlug communication standard; and a second oneof the differing PLC communication standards comprises an ITU homenetworking (G.hn) communication standard.